Skip to content

docs: add changelog entry for merge queue enqueue by label#37

Closed
mintlify[bot] wants to merge 2 commits into
mainfrom
changelog/2026-05-19
Closed

docs: add changelog entry for merge queue enqueue by label#37
mintlify[bot] wants to merge 2 commits into
mainfrom
changelog/2026-05-19

Conversation

@mintlify
Copy link
Copy Markdown
Contributor

@mintlify mintlify Bot commented May 19, 2026

Summary

Adds this week's changelog post covering the only product change merged since the last changelog entry (April 30, 2026): label-based PR enqueueing for Merge Queue.

Changes

  • New post at changelog/2026-05-19-merge-queue-enqueue-by-label.mdx written in the same style as recent entries on trunk.io/changelog
  • Organized under New features (no updates or bug fixes shipped this week)
  • Links to the docs

Context

Triggered by the merge of PR #30 (docs(merge-queue): document label-based PR enqueueing). It is the only user-facing product change shipped between April 30 and today.

@mintlify
Copy link
Copy Markdown
Contributor Author

mintlify Bot commented May 19, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview May 19, 2026, 6:56 PM

@samgutentag samgutentag added changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). ready to merge Verify docs PR: customers can use this. Ready to publish. labels May 19, 2026
@samgutentag
Copy link
Copy Markdown
Member

samgutentag commented May 19, 2026

Verification status (2026-05-26): live

Verified: customers can use this. Ready to publish.

  • Eng: trunk2#3956 (merged 2026-05-13). Feature gated by per-repo labelCommandsEnabled user setting; no LaunchDarkly flag.
  • Flag: none
  • Signals: underlying feature verified live in prior sweeps. Re-confirmed 2026-05-26.

Note: per #38's body, this draft can be closed in favor of the consolidated weekly post (#38).

Labels: ready to merge, changelog.

mintlify Bot and others added 2 commits May 26, 2026 14:19
Restructure body to canonical changelog shape: drop h2/h3 headings,
keep bold opener + paragraphs + Note callout for the cancel-caveat.
Add required `type: new-feature` frontmatter.

Wire the entry into the three sites the initial draft missed:
- docs.json nav (under Changelog tab → 2026 group, newest first)
- changelog/index.mdx (master index with tag-filter UI)
- merge-queue/changelog.mdx (product-page index; adds new May 2026
  section above April)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@samgutentag samgutentag force-pushed the changelog/2026-05-19 branch from cf8004e to 75c6c34 Compare May 26, 2026 21:27
samgutentag added a commit that referenced this pull request May 26, 2026
…ring

Adds `scripts/sync-changelog.py`, which regenerates the four sites the
changelog lives on from a single source of truth: the frontmatter of
each `changelog/*.mdx` entry. Removes the manual-maintenance burden
that came up in PR #36/#37/#39 review (each changelog PR previously
had to update docs.json + master index + product-page index in
addition to the entry file).

The script targets:
- docs.json — Changelog tab year-group `pages` arrays (surgical replace)
- changelog/index.mdx — master index with tag-filter UI
- merge-queue/changelog.mdx — entries where category = "Merge Queue"
- flaky-tests/changelog.mdx — entries where category = "Flaky Tests"

Other categories (Code Quality, CI Autopilot, Web App) appear in the
master index but have no product-page index per current convention.

Usage:
  python3 scripts/sync-changelog.py            apply
  python3 scripts/sync-changelog.py --check    CI mode; exits 1 on drift

Also commits a normalization pass on the 4 target files: same-day
entries are now sorted alphabetically by slug (was somewhat random),
and one stray blank line after frontmatter is dropped. No content
changes — all 154 entries preserved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@samgutentag
Copy link
Copy Markdown
Member

Superseded by a fresh PR using the automated changelog sync workflow from PR #74.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog PR touches the changelog (auto-generated drafts, hosting, formatting, indexing). ready to merge Verify docs PR: customers can use this. Ready to publish.

Development

Successfully merging this pull request may close these issues.

1 participant